Analyst Drive can be purchased as a standalone program which can be executed as an external program from the command line. Cube users may also find it desirable to run the Analyst Drive program from a windows command shell; this can be useful to troubleshoot issues encountered when running from Application Manager.

Another reason to run from the command line is simply where the user is performing some complex task that necessitates doing so. To run from the command line, it is good practice to put all necessary files in a working directory (similar to what you would find in a scenario directory in Cube); this includes the input files as well as a copy of the control file which must be edited to remove any catalog/scenario keys since it will be run externally from Cube and hence these key values will not be passed to the program.

If running externally from a Cube setup, it is a good idea to make a secondary copy of the control file external to the one used in Cube and in the Applications directory of your model, since it is easy to accidentally try to edit this file from Cube in which case all catalog/scenario keys in the filenames will replace the hard-coded paths that were previously edited. The WORKDIR parameter which defines the path of the working directory in this case should simply be the same as the directory folder where all files are kept. Once all files are properly set up, it is simple to execute Analyst Drive from the command line. To do this, open a windows command shell on the C: drive, and type the following commands for Analyst Drive:

The first command switches to the working directory (cd=change directory), and the second command executes the Analyst_Drive.exe program executable using the specified control file that resides in the current directory. There are other ways to accomplish the same task from the command shell as long as all file paths are defined/used correctly, but the method laid out here is the most straightforward. The default installation path for the Analyst Drive executables on a 32-bit machine is the same as for the other Citilabs programs (Cube, Voyager, etc.). In this case, Analyst_Drive.exe can be found in

If the computer where the installation is found has a 64-bit operating system, there is a separate installation directory where 64-bit-specific files and executables reside, and this is where the 64-bit version of Analyst Drive will be found:

If you do not use the default installation path and need to locate your particular installation path, you can find it simply by typing the command

As long as Analyst_Drive.exe has been properly registered by the Citilabs Cube installer, this will provide you with the correct path. If purchased as a standalone program, the installation is done manually by the user and so it will be found where they placed it.

If Analyst Drive was acquired as part of a Cube installation, it should have come with a bundled installation of the Intel MPI Library runtime environment. If purchased as a standalone program and the user wishes to use the MPICORES parameter with Analyst Drive, they will need to download and install the Intel MPI Library Runtime Environment for Windows (free download; requires email address). The commands for running the MPI version are the same as for running the base version. Note that the user may need to provide a password via the command shell when running with MPI for the first time due to access rights on particular machines.